Skip to content

[APM] Remove the java agent auto-attacher from the APM onbarding#249043

Merged
jennypavlova merged 5 commits intoelastic:mainfrom
jennypavlova:248894-apm-remove-the-java-agent-auto-attacher-from-the-apm-onbarding
Jan 15, 2026
Merged

[APM] Remove the java agent auto-attacher from the APM onbarding#249043
jennypavlova merged 5 commits intoelastic:mainfrom
jennypavlova:248894-apm-remove-the-java-agent-auto-attacher-from-the-apm-onbarding

Conversation

@jennypavlova
Copy link
Copy Markdown
Member

@jennypavlova jennypavlova commented Jan 14, 2026 •
edited by kibanamachine
Loading

Closes #248894

Summary

This PR removes the Java agent auto-attacher from the APM onboarding. The Java agent "Auto-Attachment" tab is no longer visible in the Fleet APM integration UI. All related runtime attachment components and code have been removed.
The onboarding now only shows manual instrumentation steps for all agents.

Changes:

  • Files Deleted: entire runtime_attachment/ directory + unused translations:
  • Changed to use PackagePolicyEditExtensionComponentProps for proper Fleet integration typing
  • Extracts apmServerUrl and secretToken from newPolicy and passes them to child components
  • Fixed the key prop to use ${agentName}-${variantId} for uniqueness

How to test

  • I am creating a cloud deployment with this PR and we should be able to test there

  • @jackshirazi Could you please verify if everything still works on the agent side with those changes

  • Tested on cloud

✅ Tested using the PR cloud deployment:

  • Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy -> Edit integration (Edit Elastic APM integration)
  • The Java auto-attacher tab is not present ✅
image
  • Tested with Java agent (if needed ❓)

@jennypavlova jennypavlova self-assigned this Jan 14, 2026
@jennypavlova jennypavlova requested a review from a team as a code owner January 14, 2026 15:12
@jennypavlova jennypavlova added release_note:skip Skip the PR/issue when compiling release notes backport:all-open Backport to all branches that could still receive a release ci:cloud-deploy Create or update a Cloud deployment Team:obs-presentation Focus: APM UI, Infra UI, Hosts UI, Universal Profiling, Obs Overview and left Navigation labels Jan 14, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Jan 14, 2026

Pinging @elastic/obs-presentation-team (Team:obs-presentation)

miloszmarcinkowski
miloszmarcinkowski approved these changes Jan 14, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@miloszmarcinkowski miloszmarcinkowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM (code review only)

jackshirazi
jackshirazi approved these changes Jan 15, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@jackshirazi jackshirazi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I didn't see any problems when testing with this snapshot

@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Jan 15, 2026 •
edited
Loading

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #124 / Endpoint plugin @ess @serverless @skipInServerlessMKI Endpoint execute response action "before all" hook for "should not allow execute action without required privilege"
  • [job] [logs] Scout: [ observability / observability ] plugin / should display dashboard options in related dashboards dropdown when editing rule
  • [job] [logs] Scout: [ observability / observability ] plugin / stateful - Rule Details Page - Admin - should display dashboard options in related dashboards dropdown when editing rule

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
apm 2089 2081 -8

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
apm 2.9MB 2.9MB -56.9KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
apm 36.8KB 36.8KB -10.0B
Unknown metric groups

ESLint disabled line counts

id before after diff
apm 64 63 -1

Total ESLint disabled count

id before after diff
apm 77 76 -1

History

cc @jennypavlova

@jennypavlova jennypavlova enabled auto-merge (squash) January 15, 2026 16:12
@jennypavlova jennypavlova merged commit da35df4 into elastic:main Jan 15, 2026
15 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Jan 15, 2026

Starting backport for target branches: 8.19, 9.1, 9.2, 9.3

https://github.com/elastic/kibana/actions/runs/21038488863

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jan 15, 2026
@jennypavlova
[APM] Remove the java agent auto-attacher from the APM onbarding (ela…
43a420b 
…stic#249043)

Closes elastic#248894

## Summary
This PR removes the Java agent auto-attacher from the APM onboarding.
The Java agent "Auto-Attachment" tab is no longer visible in the Fleet
APM integration UI. All related runtime attachment components and code
have been removed.
The onboarding now only shows manual instrumentation steps for all
agents.

## Changes:
- Files Deleted: entire `runtime_attachment/` directory + unused
translations:
- Changed to use PackagePolicyEditExtensionComponentProps for proper
Fleet integration typing
- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes
them to child components
- Fixed the key prop to use ${agentName}-${variantId} for uniqueness

## How to test
- I am creating a cloud deployment with this PR and we should be able to
test there
- @jackshirazi Could you please verify if everything still works on the
agent side with those changes

- [x] Tested on cloud

✅ Tested using the PR cloud deployment:
- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->
Edit integration (Edit Elastic APM integration)
- The Java auto-attacher tab is not present ✅

<img width="1913" height="1010" alt="image"
src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068"
/>

- [x] Tested with Java agent (if needed ❓)

(cherry picked from commit da35df4)
@kibanamachine kibanamachine mentioned this pull request Jan 15, 2026
Merged
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Jan 15, 2026

💔 Some backports could not be created

Status Branch Result
❌ 8.19 Backport failed because of merge conflicts
❌ 9.1 Backport failed because of merge conflicts
❌ 9.2 Backport failed because of merge conflicts

You might need to backport the following PRs to 9.2:
- [Fleet] Do not use multi page layout for hello word agentless (#249057)
- [Discover] Wrap error boundary around chartSectionConfig.renderChartSection (#249107)
- [Inference] Add maxQueue backpressure to anonymization regex worker pool (#249108)
- [Security Solution] Installation review pagination: Backend (#247375)
- Update dependency joi to ^18.0.2 (main) (#245131)
✅ 9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

node scripts/backport --pr 249043

Questions ?

Please refer to the Backport tool documentation

@jennypavlova jennypavlova mentioned this pull request Jan 15, 2026
Merged
jennypavlova added a commit to jennypavlova/kibana that referenced this pull request Jan 15, 2026
@jennypavlova
[APM] Remove the java agent auto-attacher from the APM onbarding (ela…
23b046e 
…stic#249043)

Closes elastic#248894

## Summary
This PR removes the Java agent auto-attacher from the APM onboarding.
The Java agent "Auto-Attachment" tab is no longer visible in the Fleet
APM integration UI. All related runtime attachment components and code
have been removed.
The onboarding now only shows manual instrumentation steps for all
agents.

## Changes:
- Files Deleted: entire `runtime_attachment/` directory + unused
translations:
- Changed to use PackagePolicyEditExtensionComponentProps for proper
Fleet integration typing
- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes
them to child components
- Fixed the key prop to use ${agentName}-${variantId} for uniqueness

## How to test
- I am creating a cloud deployment with this PR and we should be able to
test there
- @jackshirazi Could you please verify if everything still works on the
agent side with those changes

- [x] Tested on cloud

✅ Tested using the PR cloud deployment:
- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->
Edit integration (Edit Elastic APM integration)
- The Java auto-attacher tab is not present ✅

<img width="1913" height="1010" alt="image"
src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068"
/>

- [x] Tested with Java agent (if needed ❓)

(cherry picked from commit da35df4)

# Conflicts:
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/runtime_attachment.tsx
@jennypavlova jennypavlova mentioned this pull request Jan 15, 2026
Merged
jennypavlova added a commit to jennypavlova/kibana that referenced this pull request Jan 15, 2026
@jennypavlova
[APM] Remove the java agent auto-attacher from the APM onbarding (ela…
fe55248 
…stic#249043)

Closes elastic#248894

## Summary
This PR removes the Java agent auto-attacher from the APM onboarding.
The Java agent "Auto-Attachment" tab is no longer visible in the Fleet
APM integration UI. All related runtime attachment components and code
have been removed.
The onboarding now only shows manual instrumentation steps for all
agents.

## Changes:
- Files Deleted: entire `runtime_attachment/` directory + unused
translations:
- Changed to use PackagePolicyEditExtensionComponentProps for proper
Fleet integration typing
- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes
them to child components
- Fixed the key prop to use ${agentName}-${variantId} for uniqueness

## How to test
- I am creating a cloud deployment with this PR and we should be able to
test there
- @jackshirazi Could you please verify if everything still works on the
agent side with those changes

- [x] Tested on cloud

✅ Tested using the PR cloud deployment:
- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->
Edit integration (Edit Elastic APM integration)
- The Java auto-attacher tab is not present ✅

<img width="1913" height="1010" alt="image"
src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068"
/>

- [x] Tested with Java agent (if needed ❓)

(cherry picked from commit da35df4)

# Conflicts:
#	x-pack/platform/plugins/private/translations/translations/de-DE.json
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/discovery_rule.tsx
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/edit_discovery_rule.tsx
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/runtime_attachment.tsx
jennypavlova added a commit to jennypavlova/kibana that referenced this pull request Jan 15, 2026
@jennypavlova
[APM] Remove the java agent auto-attacher from the APM onbarding (ela…
991ded1 
…stic#249043)

Closes elastic#248894

## Summary
This PR removes the Java agent auto-attacher from the APM onboarding.
The Java agent "Auto-Attachment" tab is no longer visible in the Fleet
APM integration UI. All related runtime attachment components and code
have been removed.
The onboarding now only shows manual instrumentation steps for all
agents.

## Changes:
- Files Deleted: entire `runtime_attachment/` directory + unused
translations:
- Changed to use PackagePolicyEditExtensionComponentProps for proper
Fleet integration typing
- Extracts `apmServerUrl` and `secretToken` from `newPolicy` and passes
them to child components
- Fixed the key prop to use ${agentName}-${variantId} for uniqueness

## How to test
- I am creating a cloud deployment with this PR and we should be able to
test there
- @jackshirazi Could you please verify if everything still works on the
agent side with those changes

- [x] Tested on cloud

✅ Tested using the PR cloud deployment:
- Go to APM -> Fleet -> Agent policies -> Elastic Cloud agent policy ->
Edit integration (Edit Elastic APM integration)
- The Java auto-attacher tab is not present ✅

<img width="1913" height="1010" alt="image"
src="https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068"
/>

- [x] Tested with Java agent (if needed ❓)

(cherry picked from commit da35df4)

# Conflicts:
#	x-pack/platform/plugins/private/translations/translations/de-DE.json
#	x-pack/platform/plugins/private/translations/translations/fr-FR.json
#	x-pack/platform/plugins/private/translations/translations/zh-CN.json
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/discovery_rule.tsx
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/edit_discovery_rule.tsx
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/java_agent_version_input.tsx
#	x-pack/solutions/observability/plugins/apm/public/components/fleet_integration/apm_agents/runtime_attachment/runtime_attachment.tsx
@jennypavlova jennypavlova mentioned this pull request Jan 15, 2026
Merged
@jennypavlova
Copy link
Copy Markdown
Member Author

jennypavlova commented Jan 15, 2026

💚 All backports created successfully

Status Branch Result
✅ 9.2
✅ 9.1
✅ 8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

jennypavlova added a commit that referenced this pull request Jan 15, 2026
@jennypavlova
[9.2] [APM] Remove the java agent auto-attacher from the APM onbarding (
ecc03eb 
#249043) (#249279)

# Backport

This will backport the following commits from `main` to `9.2`:
- [[APM] Remove the java agent auto-attacher from the APM onbarding
(#249043)](#249043)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM]
Remove the java agent auto-attacher from the APM
onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},{"url":"https://github.com/elastic/kibana/pull/249264","number":249264,"branch":"9.3","state":"OPEN"}]}]
BACKPORT-->
jennypavlova added a commit that referenced this pull request Jan 15, 2026
@jennypavlova
[9.1] [APM] Remove the java agent auto-attacher from the APM onbarding (
59c516e 
#249043) (#249281)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[APM] Remove the java agent auto-attacher from the APM onbarding
(#249043)](#249043)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM]
Remove the java agent auto-attacher from the APM
onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},{"url":"https://github.com/elastic/kibana/pull/249264","number":249264,"branch":"9.3","state":"OPEN"}]}]
BACKPORT-->
jennypavlova added a commit that referenced this pull request Jan 15, 2026
@jennypavlova
[8.19] [APM] Remove the java agent auto-attacher from the APM onbardi…
0cc6af9 
…ng (#249043) (#249282)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[APM] Remove the java agent auto-attacher from the APM onbarding
(#249043)](#249043)

<!--- Backport version: 10.2.0 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM]
Remove the java agent auto-attacher from the APM
onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},{"url":"https://github.com/elastic/kibana/pull/249264","number":249264,"branch":"9.3","state":"OPEN"}]}]
BACKPORT-->
kibanamachine added a commit that referenced this pull request Jan 16, 2026
@kibanamachine @jennypavlova
[9.3] [APM] Remove the java agent auto-attacher from the APM onbarding (
2a5843b 
#249043) (#249264)

# Backport

This will backport the following commits from `main` to `9.3`:
- [[APM] Remove the java agent auto-attacher from the APM onbarding
(#249043)](#249043)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT
[{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2026-01-15T16:25:29Z","message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4","branchLabelMapping":{"^v9.4.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","ci:cloud-deploy","v9.4.0","Team:obs-presentation"],"title":"[APM]
Remove the java agent auto-attacher from the APM
onbarding","number":249043,"url":"https://github.com/elastic/kibana/pull/249043","mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.4.0","branchLabelMappingKey":"^v9.4.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/249043","number":249043,"mergeCommit":{"message":"[APM]
Remove the java agent auto-attacher from the APM onbarding
(#249043)\n\nCloses #248894\n\n## Summary\nThis PR removes the Java
agent auto-attacher from the APM onboarding.\nThe Java agent
\"Auto-Attachment\" tab is no longer visible in the Fleet\nAPM
integration UI. All related runtime attachment components and code\nhave
been removed.\nThe onboarding now only shows manual instrumentation
steps for all\nagents.\n\n## Changes: \n- Files Deleted: entire
`runtime_attachment/` directory + unused\ntranslations:\n- Changed to
use PackagePolicyEditExtensionComponentProps for proper\nFleet
integration typing\n- Extracts `apmServerUrl` and `secretToken` from
`newPolicy` and passes\nthem to child components\n- Fixed the key prop
to use ${agentName}-${variantId} for uniqueness\n\n## How to test\n- I
am creating a cloud deployment with this PR and we should be able
to\ntest there\n- @jackshirazi Could you please verify if everything
still works on the\nagent side with those changes\n\n- [x] Tested on
cloud\n\n✅ Tested using the PR cloud deployment: \n- Go to APM -> Fleet
-> Agent policies -> Elastic Cloud agent policy ->\nEdit integration
(Edit Elastic APM integration)\n- The Java auto-attacher tab is not
present ✅ \n\n<img width=\"1913\" height=\"1010\"
alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2bf9d0ad-ecc2-44b9-b6b9-fc3eeac9d068\"\n/>\n\n\n-
[x] Tested with Java agent (if needed
❓)","sha":"da35df416e9ac9e5c4145828cd69dccc32ebffb4"}}]}] BACKPORT-->

Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jackshirazi jackshirazi jackshirazi approved these changes

@miloszmarcinkowski miloszmarcinkowski miloszmarcinkowski approved these changes

Assignees

@jennypavlova jennypavlova

Labels

backport:all-open Backport to all branches that could still receive a release ci:cloud-deploy Create or update a Cloud deployment release_note:skip Skip the PR/issue when compiling release notes Team:obs-presentation Focus: APM UI, Infra UI, Hosts UI, Universal Profiling, Obs Overview and left Navigation v8.19.11 v9.1.11 v9.2.5 v9.3.0 v9.4.0

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[APM] Remove the java agent auto-attacher from the APM onbarding

5 participants

@jennypavlova @elasticmachine @kibanamachine @jackshirazi @miloszmarcinkowski